wsarchie.zip can be found at ftp.sunet.se /pub/pc/windows/wsarchie
burt154@telerama.lm.com
From news@bigblue.oit.unc.edu Wed Mar 30 21:14:43 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
id AA14476; Wed, 30 Mar 1994 20:42:05 -0500
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
id AA27605; Wed, 30 Mar 1994 20:27:26 -0500
Received: from GATEWAY by bigblue with netnews
for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu)
To: winsock@sunsite.unc.edu
Date: 30 Mar 1994 21:14:43 GMT
From: gerry@stars1den.mmc.com (Gerry VonRiesen)
Message-Id: <2ncq43$c2f@louie.udel.edu>
Organization: Martin Marietta Astronautics
Sender: ses
Subject: Visual Basic calling Winsock.DLL
I am trying to write a VB application calling a winsock DLL. I can call the DLL
but am having problems using what it returns. The DLL returns a pointer to an
array. How can I use this pointer to access the data in the array????
Are there any VB wizards out there!!!!!!
From news@bigblue.oit.unc.edu Tue Mar 29 06:00:46 1994
Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
id AA14493; Wed, 30 Mar 1994 20:42:07 -0500
Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
id AA29469; Wed, 30 Mar 1994 20:35:05 -0500
Received: from GATEWAY by bigblue with netnews
for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu)
To: winsock@sunsite.unc.edu
Date: Tue, 29 Mar 1994 06:00:46 GMT
From: teh@latcs2.lat.oz.au (Richie L C TEH)
Message-Id: <CnEwpA.DG9@latcs1.lat.oz.au>
Organization: Comp Sci, La Trobe Uni, Australia
Sender: ses
Subject: Help: Winsock crashes Workgroups
Hi,
I've been having problems with running the Winsock version of QVT ver
3.96, on Windows for Workgroups ver3.11 in NDIS2/NDIS3 mode with protocols
IPX/SPX, NetBeui and Microsoft TCP/IP.
Firstly, the FTP option. If I were to upload or download a large number of files (binary or text) to and from the Unix box, my windows system usually
crashes after it's done approx 3/4 of the files. Seems like a winsock problem.
The other problem lies with telnet. If I would to telnet to a site the
first time, do some work, than exit, and then repeat this process for around,
say 10 times, it'll crash windows.
You might be wondering why am I wasting my time to try and crash windows, the reason is because I suspect that winsock provided by Microsoft is pretty
unreliable. The reason I brought this up is not to upset anyone, but to find
out how I could justify this problem. Who knows, I might have setup the system wrongly. Another reason why I suspect winsock, is because we've writed a program
that uses Winsock API to communicate between PCs in the windows environment.
When executing the problem, we tried establishing the connection, then shutting it down, and then repeatibng the process. On the third and fourth try, it usually crashes windows. We checked our program thoroughly, and found nothing wrong with it. We then decided to try a working winsock program - thus wsqvt, and that
crashes as a result.
Can someone enlighten me? Sorry for the lengthy mail.